|
|
|
|
|
|
|
Processing Funds Transaction |
|
|
|
|
|
|
|
|
Assessing the exact forms to design is usually difficult for most Visual Basic applications you develop. It is common to have one form per use case. However, some use cases are used by others. This means that if Use Case A has a Form A and uses Use Case B, assuming Use Case B has a Form B, there would need to be a command button on Form A whose controller invokes a method on the controller of Form B in order to show Form B. |
|
|
|
|
|
|
|
|
Every application has an implied use of the system for starting up the system and shutting it down. Although you can certainly have formal use cases for these business tasks, scenario scripts are acceptable. Ignore the script for shutting down the application for the Bank example. The scenario script for starting the application is as follows: |
|
|
|
|
|
|
|
|
1. From the desktop, choose the application icon. |
|
|
|
|
|
|
|
|
2. Initialize global object variables. |
|
|
|
|
|
|
|
|
3. Display the main form. |
|
|
|
|
|
|
|
|
Notice step 3. When you document your use cases, you will seldom mention any kind of main form, just business processes. Nevertheless, as is the case with all GUI applications, the user wants all major business processes supported in the application to be instantly accessible when the application starts. For the Bank example, your startup form will be an MDI form. Given this, you come up with the set of forms in Table 12.1. |
|
|
|
|
| TABLE 12.1. THE INITIAL SET OF FORMS FOR THE SAMSONA BANK TELLER SYSTEM. | | Form Name | Caption | | frmDeposit | Deposit New Funds | | frmOpenAccount | Open an Account | | frmWithdraw | Withdraw Funds | | frmCloseAccount | Close an Account | | frmCancelTransaction | Cancel a Transaction | | frmCheckAccountStatus | Check Status of Account | | frmMDI | Samsona Bank Teller System |
|
|
|